Root cause

Entity, observation, and relation rows in search_index carry ids from independent auto-increment sequences, so rows of different types routinely share the same numeric id — guaranteed in young databases. In src/basic_memory/repository/search_repository_base.py:

1. _search_vector_only parsed each vector hit's chunk_key (e.g. entity:4:0) but discarded the type, keying similarity_by_si_id / chunks_by_si_id by bare id, which also collapsed colliding hits into one map slot.
2. _fetch_search_index_rows_by_ids fetched WHERE id IN (...) and keyed its result dict by bare row.id — whichever row the database returned last clobbered the other, so the clobbered hit hydrated against the wrong row or was silently dropped (e.g. an entity vanishing entirely under a search_item_types filter when a relation shared its id).
3. _search_hybrid fused FTS and vector results on bare row id, merging unrelated rows of different types and granting them a spurious dual-source fusion bonus.

The FTS-filter branch already guarded exactly this with (id, type) tuples — the primary vector lookup path and hybrid fusion missed the same treatment.

Fix

Introduce a SearchIndexKey = tuple[str, int] type alias and key every map in the vector/hybrid retrieval path by (type, id): the similarity and chunk maps in _search_vector_only, the _fetch_search_index_rows_by_ids result, the FTS-filter allowed-keys set, and the rows/fts/vec/fused score maps in _search_hybrid. SQL stays unchanged; bare ids are deduplicated before the IN query and rows are discriminated by row.type when building dict keys. The fix lives in the shared base class, so both SQLite and Postgres backends are covered.

Test evidence

• test_sqlite_vector_search_survives_cross_type_id_collision (real SQLite + sqlite-vec harness): indexes an entity row and a relation row sharing id=7, syncs vectors for both, asserts vector retrieval returns both rows with correct types, and that a search_item_types=[ENTITY] filter still returns the entity.
• test_cross_type_id_collision_keeps_both_results (hybrid fusion): an FTS entity and a vector relation sharing id=1 stay distinct with their single-source scores — no cross-type merge or fusion bonus.
• Both tests fail on main without the src change (verified by stashing the fix: SQLite test returns 1 merged result instead of 2; hybrid test fuses the rows into one) and pass with it.
• Existing mocked vector tests (test_vector_threshold.py, test_vector_pagination.py) updated for tuple-keyed fetch results.
• 415 passed / 19 skipped across tests/repository/, search service, semantic search, and search schema suites; ruff and ty clean on src tests test-int.

Fixes #982

🤖 Generated with Claude Code